Curating communications

ABSTRACT

A computer-implemented method includes notifying a first person that a significant event is going to occur with respect to a second person; receiving from the first person, the second person, or another person a communication that relates to the significant event and to the first person and that has been curated at least in part from information that has been accumulated automatically from online resources; and sending the curated communication to the communication target.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part application of and claimspriority to U.S. application Ser. No. 13/489,210, filed on Jun. 5, 2012,the entire contents of which are incorporated here by reference.

BACKGROUND

This description relates to communicating information about one party toanother party.

A typical user of a social networking website communicates with otherusers of the social networking website by posting information abouthimself or information of interest to other users of the social networkwebsite in a manner that is accessible to the other users. For example,a user of a social networking website might post background informationabout himself, such as current job or activity information; informationabout events attended, such as concerts; events the user plans toattend, such as travel vacation sites; or personal events, such asbirthdays or anniversaries. A user may also post information aboutrecent acquisitions, such as the purchase of a new automobile orsmartphone. Other users who have access to the user's posted informationmay contact the user to comment or review information about commonshared interests or for other reasons.

Some social networking websites filter or group connections based on,e.g., friendship, profession or job type, or geographical location.Social networks often span users within a single generation (e.g.,Generation X or Generation Y) or at least within a limited agedemographic.

SUMMARY

In a general aspect, a computer-implemented method includes notifying afirst person that a significant event is going to occur with respect toa second person; receiving from the first person, the second person, oranother person a communication that relates to the significant event andto the first person and that has been curated at least in part frominformation that has been accumulated automatically from onlineresources; and sending the curated communication to the communicationtarget.

Embodiments may include one or more of the following.

The method further includes detecting an occurrence of the significantevent. In some cases, the method further includes receiving informationprovided by the first person defining at least one condition foroccurrence of the significant event. In sonic cases, detecting anoccurrence of the significant event includes conducting an automatedanalysis of publicly available (a) online or mobile social networkingfacilities, (b) online or mobile periodicals, and (c) websites.

Receiving the communication includes receiving an approval of anautomatically generated communication.

Receiving the communication includes receiving a communication that hasbeen generated by the first person and that includes at least sonic ofthe information that has been accumulated.

The method further includes receiving an identification of the secondperson from the first person.

In another general aspect, a computer-implemented method includes, inconnection with an occurrence of a significant event of a person theconditions for occurrence of which had been defined earlier by a user,automatically generating a page of a website or a mobile application oran email application that is associated with the significant event ofthe person and includes information generated by and received from theuser, information about, the person, and information associated with theperson that has been obtained by automated analysis of publiclyavailable (a) online or mobile social networking facilities, (b) onlineor mobile periodicals, and (c) websites, and serving the page fordisplay through a web browser or a mobile application or an emailapplication.

Embodiments may include one or more of the following.

The page is served after the user is given an opportunity to curate thepage.

Curating the page includes adding content to the page, removing contentfrom the page, and/or changing content on the page.

The page is served to an editor and then re-served after the editor hascurated it, and the editor is designated by the user.

The page is served without input from the user.

Notification of the occurrence of the significant event is givenautomatically to someone, in particular someone who needs to take someaction regarding the event. In sonic cases, notification of theoccurrence of the significant event is given automatically to the user.

The method further includes detecting the occurrence of the significantevent.

Detecting the occurrence of the significant event includes conducting anautomated analysis of publicly available (a) online or mobile socialnetworking facilities, (b) online or mobile periodicals, and (c)websites. In some cases, conducting an automated analysis includesconducting the analysis in view information provided by the userdefining the conditions for occurrence of the event.

The page is served in the future to parties whose existence and identitywith respect to the user and the significant event is undetermined atthe time when the conditions for occurrence are defined.

The user is a service provider and the person is a client of the serviceprovider.

The user is an agent of a company, the person is an employee of thecompany, and the page is served as a corporate email message or as awebsite on an internal corporate network.

The user is an agent of a charitable foundation or university and theperson is a donor to the charitable foundation or university.

The page includes information that is generated by and received fromanother user and is about the person.

The page includes information that is generated by and received from theperson and is about the person.

The event is a death of the person.

Serving the page includes serving the page to a relative of the person.

The event is a birthday or anniversary of the person.

The event is a change in employment status of the person.

Serving the page includes delivering a notification of the page to arecipient via a private communication.

The recipient is the person.

The private communication channel includes email, telephone, shortmessage service (SMS) messaging, and/or social network facilitatedcommunication.

Serving the page includes publishing the page as a website.

The website is available to a group of people sharing a commonaffiliation.

These and other aspects, features, implementations, and advantages, andcombinations of them, can be expressed as methods, apparatus, systems,components, program products, business methods, and means or steps forperforming functions, or combinations of them.

Other features, aspects, implementations, and advantages will becomeapparent from the description, the drawings, and the claims.

DESCRIPTION

FIG. 1 is a functional diagram of the system actions for communicatingmessages.

FIG. 2 is an example of a document generated by the system formultimedia communications.

FIG. 3 is a block diagram of a system for communicating messages.

FIG. 4 is a block diagram of a life event storage module.

FIG. 5 is view of a publisher interface.

FIG. 6 is a view of an editor interface.

FIG. 7 is a block diagram of a Notification Engine.

FIG. 8 is a block diagram of a Communication Engine.

FIG. 9 is a block diagram of an Analytics Engine.

FIG. 10 is a view of a reader display.

FIG. 11 is a flowchart of a process for publishing a communication inresponse to a life event.

FIG. 12 is a flowchart of a process for publishing a comment on acommunication in response to a life event

FIG. 13 is a flowchart of a process Err transferring an itemaccompanying a communication in response to a life event.

The system that we describe here enables a person (sometimes called acurator) to generate and/or curate a message (e.g., a multimediamessage) to be published or to be delivered to one or more other peoplein response to a significant event (e.g., a life event such as abirthday, marriage, anniversary, death, or other life event; a promotionor other change in employment status; or another event, such aspurchasing a car or voting in an election) of the person generating themessage, the person receiving the message, or another person. Wesometimes refer to such a person as the “significant event person”. Forinstance, the system described here can be used to automatically deliverbirthday greetings, sympathy messages, messages of congratulations, carobituaries to the recipient. We sometimes refer to such messages ascommunications. The message can be communicated in the present or atfuture times, e.g., at a time that is suggested by or associated withthe significant event, which may have already occurred or which mayoccur in the future. The system is able to automatically detectoccurrence of such a significant event and to populate the message or adraft of the message with content generated by the person generatingand/or curating the message and content obtained via automated analysisof various sources of information, such as websites, publications,social networks, and other online sources, among others.

FIG. 1 is a functional diagram of an example of process forcommunicating items, e.g., communicating messages (e.g., multimediamessages) about significant events from a publisher user to a readeruser, using a system 300. A Significant Event Person 102, the associatedtrigger event, and any requisite action(s) are identified forregistration in a Notification Engine 108 (step 104). The identificationmay rely on the publisher's direct personal knowledge of the SignificantEvent Person 102 and may sometimes be assisted by an interest profileand status information about the Significant Event Person 102 obtainedfrom a Communication Engine 110, information about the significant eventperson 102 determined analytically by an Analytics Engine 106, or both,in an automated fashion as described in more detail below. The triggerevent may be an event with a definite date such as a birthday. Thetrigger event may also be an event with a threshold probability foroccurrence, such as a point in time at which the significant eventperson has a high propensity for purchasing an automobile. When thetrigger event occurs, the Notification Engine 106 notifies the publisher(step 112), allowing the publisher to generate and curate a message fora Reader 120 (step 114), who may or may not be the significant eventperson. Curating the message may be aided by an interest profile andstatus information of the Reader 120 and/or the significant event personobtained from a Communication Engine 110 or information determinedanalytically from various sources about the Significant Event Personand/or Reader from an Analytic Engine 106 or both in an automatedfashion as described in more detail below. The curated message may besubject to Editing (step 116) by one or more editors 320, includingreviewing, revision, and/or commenting. The editors 320 may also beaided by the interest profile and status information of the Reader 120and/or the significant event person obtained from a Communication Engine110 or information determined analytically from various sources aboutthe Significant Event Person 102 and/or the Reader 120 from an AnalyticEngine 106 or both m an automated fashion as described in more detailbelow. The curated and possibly edited message Communicated (step 118),including delivery of the message to the reader 120 and/or thesignificant event person and/or publication of the message. Thecommunication of the message may be aided by interest profile and statusinformation of the Reader 120 and/or the significant event personobtained from a Communication Engine 110 or information determinedanalytically from various sources about the Reader 120 and/or thesignificant event person from an Analytic Engine 106 or both in anautomated fashion as described in more detail below.

FIG. 2 is an example of a media message 200 curated for a SignificantEvent Person. In this example, the media message 200 is a birthdaygreeting for a person named John, where John is both the significantevent person and the reader. The media message 200 consists of abackground 202 upon which are superimposed one or more verbal/textmessages 212 together with one or more objects 206 and 208 with varyingcomponents 204, 210. In this example, the curator has superimposed theimage of an object the birthday cake, 206 upon a patterned coloredbackground 202 then added animated elements including the flamingcandles 204 and a video clip 208 of friends singing “Happy Birthday,”which can be initiated by a video start control 210.

In another example involving purchasing cars, the Significant EventPerson 102 and the Reader 120 each represent classes of individuals andthe communication process relies heavily on automated support providedby the system. To identify the triggering event (i.e., a likely time atwhich a car will be purchased), the Analytic Engine 106 uses historicaldata regarding past purchases obtained from profiles collected by theCommunication Engine 110 to enable predictive analytics (e.g., asdiscussed in greater detail below) to determine the joint propensity ofthe Significant Event Person to purchase a particular brand ofautomobile at a particular time of year. Notification to theCurator/System occurs at a point in time (e.g., in March) when thatjoint propensity reaches a predetermined threshold level determined bythe Notification Engine 108. Curation of a message involves automatedgeneration of a personalized marketing letter to the Reader for thebrand of automobiles, in some cases with collateral material, such as anadvertising brochure or a $500 Discount coupon. Curation of the messageis supported by information determined by the Analytics Engine 106 andpersonal profile information determined by the Communication Engine 110.This automated curation process may be sampled by an Editor for qualitycontrol.

As used here, the term publication refers broadly to, for example,distribution of the communication to the public, e.g., on a publicallyavailable website; or to a relatively large number of people, e.g., onan internal corporate website accessible to some or all employees of thecorporation. The term delivery refers broadly to, for example, deliveryof the communication to one or more particular recipients via a privatecommunication, such as via email, short message service (SMS) messaging,telephone, communication via a social networking service, or anothertype of private communication.

In general, a publisher user retains oversight over the generation andcuration of the message. For instance, the publisher user may identify aperson whose significant event is to be identified, specify the contentof and/or delivery options for the message, and otherwise oversees themessage. We use the term publisher broadly to include, for example, aparty that is going to make it communication publicly available and alsoto a party who is going to send a message privately to one or morespecific targets. An editor user may also be involved in the curation ofthe message, e.g., by reviewing the message and then adding or removingmaterial from an automatically generated message. In some examples, thepublisher user and the editor user are the same user. The recipient ofthe message is referred to as the reader user. In some examples, themessage is generated by the publisher user and/or the editor user basedon background information provided by the system. In some examples, themessage is automatically drafted in the name of the publisher user, andthe message is subject only to brief review by the publisher user and/orthe editor user.

In some examples, the system is implemented in the context of a socialnetwork, in which one or more of the publisher user and the reader useris a member of a community of users of a network, for example, serviceproviders and clients, employees of a corporation, members of acommunity that includes multiple generations of an extended family, agroup of friends or any other group of people or entities known orunknown to each other, and combinations of any two or more of those. Inother examples, none of the users has a membership in or otheraffiliation with a social network. Implementations of the system are notlimited to social networks. For instance, the system may allow apublisher user to create an account with the system to generate thecommunication item without joining a social network and/or may allow apublisher user to interact with the system as a guest without creatingan account. The system may also allow the communication item to be sentto reader users who do not belong to a social network or who are notenrolled in the system.

The publisher user(s) and reader user(s) of a particular communicationitem may be related in any of a variety of ways, including, e.g., asfamily members (of a single generation or of multiple generations),friends, members of an interest group, employees of the samecorporation, or any other type of relationship, and may or may not bemembers of the same social network or of any social network.

In an example implementation of the system, publication of a multimediamessage (which we also refer to as a communication item) occurs at afuture time associated with a significant event of a person about whomor for whom a publisher user is constructing the communication item. Thepublisher user is, e.g., the person or entity that arranges for orcauses publication or delivery of the communication item. For instance,the publisher user may be a service provider, such as attorney, thatarranges for a congratulatory message to be sent whenever one of hisclients is promoted. As another example, the publisher user may be agrandfather that arranges for birthday greetings to be sentautomatically to each of his grandchildren on the appropriate date.

An editor user, who may be designated by the publisher user, reviews,edits, and/or comments on the message prior to publication or deliveryof the message. For example, if the publisher has composed his lifestory for future publication as his obituary, an editor may beauthorized to review and revise the communication in keeping with socialnorms or family sensibilities and/or may be permitted to add his ownobservations about significant events of the publisher. As anotherexample, the editor user may be the attorney's associate or assistantwho proofreads the message and confirms the accuracy of the statementsmade in the congratulatory message prior to delivery of the message.

Once published or delivered, the communication item is read by a readeruser at the communication time. The communication time can be a specificday (e.g., the reader user's birthday) and even a specific time on aspecific day (e.g., on the morning of the reader user's birthday), orcan be defined less specifically as a period of time (for example,during a grandchild's 13^(th) year) or as an event (e.g., upon themarriage of the fourth great-grandchild).

One or more of the publisher user, editor user, and/or reader user mayhe the same person. For instance, the publisher user and the editor usermay be the same person, or the reader user may be the publisher user inthe future (e.g., if the publisher user wants to send himself acommunication item for his own 50^(th) birthday). In addition, theperson whom the communication item is about may be none of the publisheruser, the editor user, or the reader user. For instance, the publisheruser may be a son who is preparing an obituary about his deceased fatherfor distribution to the family and friends (the reader users) of thefather.

The content of the communication item may be about the publisher user,the editor user, the reader user, and/or another person. For instance,if the communication item is a birthday greeting to the reader user fromthe publisher user, the communication item may include, e.g.,photographs of the reader user or an anecdote written by the publisheruser about an experience the publisher user and the reader user shared.As another example, if the communication item is an obituary for thedeath of the publisher user's father, the communication item may includeinformation about the life of the father but no information about eitherthe publisher user or the reader users, who are the father's family andclose friends. As still another example, if the publisher user is usingthe system to prepare his own future obituary, then the communicationitem will include information about the publisher user but noinformation about the reader users, who will be the close friends andfamily of the publisher user.

In some cases, one or more of the publisher user, the editor user, andthe reader user are members of the community served by the network, andwe sometimes use the terms publisher users or editor users or readerusers and members interchangeably. However, the publisher user and/orreader user need not have been or be a member of the network community.For example, when a grandfather, who is not a member of the networkcommunity, dies, his son, who is a member, may assemble a multimediamessage about the grandfather's significant events and publishes themedia message on a website for the grandfather's not yet livinggreat-grandchildren, who may never be members of the network.

In sonic instances, deliveries (we sometimes refer to communications asdeliveries) maybe scheduled for events such as, e.g., the death of anindividual; birthdays, anniversaries, bar mitzvahs, first communions, orother special occasions; a high school or college graduation; the birthof a child; or an accomplishment such as a promotion or attainment of anachievement or award. More generally, deliveries may be scheduled at anytime pre-specified by the publisher user in general or specific terms.The form or context of the communications made using the system may bemultimedia messages, and other types of communications. Thecommunication items can be an unlimited variety of communications, andother items.

In some examples, the communication time is named specifically inadvance, e.g., by the publisher user. For instance, the publisher usermay specify that the communication time is Jan. 17, 2013. In otherexamples, conditions for determining the communication time can bedefined, e.g., by the publisher user. For instance, the publisher usermay specify that the communication item is to be published or deliveredupon the death of a particular person without specifying the exact date.Upon detecting the person's death, the system notifies the publisheruser to publish or deliver the communication item and/or automaticallypublishes or delivers the communication item. In still other examples,the communication time can be determined later by the system itself orby the system with the help of others. For instance, the system maydetect the occurrence of a significant event of a person named as aperson of interest by the publisher user (e.g., the publisher userspecifies a particular client as a person of interest, and the systemdetects when the client receives a promotion).

A Notification Engine 108 of the system determines an appropriatedelivery date to be used as the communication time by detecting theoccurrence of a significant event (e.g., any significant event or aparticular significant event specified by the publisher user). Theengine can base this determination, for example, on data associated withthe reader user, predetermined criteria specified by the publisher user,and/or other information. In some examples, the engine detects theoccurrence of a significant event by monitoring publicly availablesources of information or private sources of information to which theengine has been granted access. These sources of information include,e.g., online or mobile social networking facilities, online or mobileperiodicals (e.g., newspapers, magazines, scientific journals,university alumni magazines, newsletters of interest groups, and otherperiodicals), and/or websites. For instance, if the publisher user hasspecified a list of individuals of interest for whom he wants to bealerted to all detected significant events, the system monitors thesources of information to detect the occurrence of a significant eventfor any of the specified individuals, such as a promotion, an award, ora death (e.g., by detecting a press release describing the person'spromotion, a newspaper article about the person's award, or an obituarypublished in a local newspaper). As another example, if the publisheruser has specified an person and a particular significant event thebirth of the person's first child), the system monitors the sources ofinformation to detect when the child is born (e.g., by detecting astatus update on a social networking facility).

At the communication time (e.g., at the date or time specified by thepublisher user and/or upon occurrence of a significant event detected bythe system), the communication item is published or delivered. Thecommunication item includes information generated by, received from,about the reader user, and/or otherwise associated with the reader user,the publisher user, and/or another person (e.g., the person whosesignificant event triggered the communication). The communication itemmay be a page of a website, a mobile application, or an emailapplication. For instance, the communication item may be acongratulatory email sent to the reader user on his birthday, or may bea welcome website provided to a new employee on his first day at his newjob. The communication item may be or include, e.g., verbalcommunications, such as text, digitized handwriting, voice recordings,or other types of digital speech; photographs, such as scanned physicalphotographs and other digital images; video, other media formats thatcan be served over the Internet or another type of communicationsnetwork; or other types of communications.

In some cases, the entire communication item has been prepared andassembled prior to the communication time. For instance, the publisheruser may have specified the exact content of a message to becommunicated (e.g., the publisher user prepares a standard birthdaygreeting message that is to be sent to each of a list of individuals ontheir birthday). In other cases, some or all of the communication itemis prepared by the publisher user and/or by the system at thecommunication time. For instance, at the communication time, thepublisher user or editor user may be prompted to modify or add contentto a previously prepared message or to confirm that the previouslyprepared message is up-to-date. As another example, the PredictiveAnalytics Engine 106 may assemble some or all of the message at thecommunication time based on previously collected data and/or datacollected at the communication time.

The Predictive Analytics Engine 106 may generate some or all of themessage based on data associated with the reader user, the publisheruser, and/or another person (e.g., the person whose significant eventtriggered the communication) and/or based on predetermined criteriaspecified by the publisher user or by the system. For example, thePredictive Analytics Engine 106 conducts an automated analysis ofpublicly available and/or private sources of information to which it hasaccess, including, e.g., online or mobile social networking facilities,online or mobile periodicals, and/or websites to identify information tobe included in the communication item. For instance, upon the death ofan individual specified by the publisher user, the Predictive AnalyticsEngine 106 prioritizes and selects information collected by theCommunication Engine 110 about the individual, including, e.g., a listof the individual's awards, publications, employment history, familyconnections, and/or other information.

The reader users may be specified by the publisher user and/orrecommended by the system. For instance, the publisher user may specifythat the communication item is a birthday greeting to be sent to hismother, who is the reader user. As another example, the publisher usermay specify that a new employee greeting be sent to all new employees(the reader users) of a corporation without specifying the exactidentity of the new employees; in this case, the system detects theidentities of the new employees (e.g., based on analysis of humanresources databases to which it has access). In still another example,the communication item is an obituary, the publisher user specifies onlythat the reader users are to be close friends and family members of thedeceased, and the system identities close friends and family members ofthe deceased based on analysis of social networking activity of thedeceased.

Thus, the publisher user is able to specify the content of thecommunication items, the communication times, and/or the readers of thecommunication either specifically or by criteria that can be used todetermine the specific items, times, and/or readers. In someimplementations, an engine, for example, an Analytics Engine, canparticipate in the determinations. In some cases, people other than thepublisher can have a role. For instance, editors designated by thepublisher may revise or comment upon a communication item. As anotherexample, a parent of a child designated as a reader may be authorized toparticipate in the determination of when the child will receive acommunication item and the content of the item to be communicated.

The layout of the communications, including, e.g., the relativepositions of the various types of information included in thecommunication item, may be specified by the publisher user, arrangedautomatically by the system, or some combination of the two. Forinstance, the system may prepare a draft communication based on astandard template and offer the publisher user the opportunity to alterthe layout of the communication prior to publication or delivery.

In some examples, the predictive Analytics Engine may recommend actionsto be taken. For example, if a deceased individual has requesteddonations to a named charitable foundation lieu of flowers, a suggestionto donate to the named charity may be included in the communicationitem. The actions may be recommended based on a statement from thepublisher user (e.g., the publisher user states his own preferences tobe recited in his obituary upon his death) or may be recommended basedon an automated analysis (e.g., the Analytics Engine may determine thecharitable intentions of the deceased by analyzing an obituary in alocal newspaper). The actions may also be recommended based on thesystem's knowledge of another party. For instance, the system mayrecommend a particular charity for donations on behalf of the deceasedby analyzing the profile and/or affinities of the deceased or thedeceased's next of kin.

In some examples, when the delivery date (we sometimes refer to thecommunication time as the delivery date) occurs, the reader user may benotified by the system) and delivery of the communication item can bearranged, if appropriate. For instance, the system may send an email tothe reader user directing the reader user to visit a specified webpageto view the communication item, in some cases, delivery notification ofthe communication item may be given by a member of the network to anon-member (e.g., from a parent who is a member to her four-year-olddaughter, who is not), or to a member as a proxy for a non-member (e.g.,to a parent as a proxy for her daughter).

In some cases, materials are stored in a storage module, e.g., in adigital capsules associated with the publisher user's account with thesystem. In some cases, the publisher user may be provided with a promptto prepare material for inclusion in the communication item or to beused to prepare a communication at a later date. For instance, adifferent subject may be provided regularly, such as monthly, as aprompt to the publisher user. Example subjects may include questionsabout what the user hopes or expects to see or experience in the future(e.g., what the user hopes to accomplish within the next year);questions about the use's personal thoughts (e.g., what are the user'sfavorite things, which ethnic or religious groups does the user identifywith); questions about current events (e.g., the user's opinion about acurrent election or political controversy); questions about the user'sdaily life (e.g., a description of “a day in the life” of the user); orother prompts. The subjects may be provided uniformly to all publisherusers who maintain significant event records, or the subjects may betailored to each user or to a subgroup of users (e.g., children mayreceive different prompts than adults). Other digital materials may alsobe stored in a user's digital account, including, e.g., digitalphotographs, digital audio, digital videos, scanned documents (e.g.,scanned copies of a graduation program),recordings of conversations, andother types of digital materials. In some examples, the user can emailor upload the digital material to a server of the system, which storesthe material in the user's digital capsule.

In some embodiments, the system may provide a phone number that a usercan dial to have a conversation recorded and stored directly in theuser's digital capsule. The phone number may be a general phone numbersuch that the user enters an identification code in order to access hisaccount; or the phone number may be a phone number specific to the user.When the user dials the phone number, he may be presented with a prompt,such as the example prompts listed above; or he may be given theopportunity to record an open-ended conversation. The user may beprompted to dial the phone number, e.g., by an email message, a shortmessage service (SMS) message, or a phone call. In some cases, the usermay be prompted to select what to do with the recording, such as whenand to whom to release the recording. The contents of the digitalcapsule may be accessed by the publisher user when preparing acommunication item. For instance, the user may want to includephotographs of a memorable vacation in a birthday greeting for hismother. The digital capsule itself may also be a communication item tobe published or delivered to a reader user. In general, the digitalcapsule and its contents can be subjected to instructions of thepublisher user about the reader or readers, the editor or editors, thecommunication time, and other information that will control the use ofthe digital capsule and its contents.

In one specific example, the system is employed by an attorney tomonitor and send messages for notable significant events for each of hisclients. The attorney provides a list of clients and a list of notablesignificant events to be monitored by the system, such as employmentpromotions and new jobs. When the system detects that, for instance, oneof the listed clients has been promoted, the Notification Engine 108notifies the attorney that such event has occurred for that client. Theattorney composes a message of congratulations to the client based onbackground information provided by the system, such as information aboutthe client (e.g., news clippings about the promotion or about theclient's recent awards) analyzed by the Analytics Engine 106. Forinstance, the attorney may include in the message suggestions ofadditional projects involving that attorney's work that are nowpertinent to the client's new position. The communication item isreviewed by the attorney's associate, whom the attorney has designatedas an editor. Upon making any necessary corrections, the attorneyarranges for the communication item to be sent to the client, e.g., bysending an email to the client using the best address determined by aCommunication Engine 110 of the system or by instructing the system tosend an email on his behalf.

In another specific example, a university maintains, in the system, alist of major donors to the university. If the Notification Engine 108detects the death of one of the individuals on the list, informationabout that individual is ordered and selected by the Analytics Engine106 and provided to the publisher user (e.g., an agent of the universitywho specified or maintains the list). The publisher user composes(curates) a sympathy message to be sent to the donor's next of kin orother close family members, who are identified and located by theCommunication Engine 110. In addition, the publisher user may instruct avendor such as a florist to send an appropriate arrangement of flowersor may make a contribution to an appropriate charity in the name of thedeceased, e.g., based on a recommendation by the Analytics Engine 106.

In another specific example, the system is used by the Human Resources(HR) Department of a corporation to send a welcome message to each newemployee on his first day of work. In some cases, the HR departmentprovides a list of newly hired individuals and a list of associatedstart dates. In other eases, the system is given access to HR databasesor other corporate databases and the Analytics Engine 106 determines,from the information in the databases, the identity and start date ofthe new employees. On the start date of each new employee, theNotification Engine 108 triggers the automated assembly, by theAnalytics Engine 106, of a welcome message. The welcome message is basedon a template and includes a message from the president of thecorporation or chairman of the board, depending on the rank of the newlyhired individual. The welcome message also includes relevantprofessional information about the new employee collected by theCommunication Engine 110 from various data sources, such as theemployee's social networking profile, the employee's publicallyavailable resume, and scientific journals or news publications includingarticles written by the employee. The automatically generated message isreviewed and approved by an editor user, such as an HR employee. Thesystem then publishes or delivers the approved personalized welcomemessage (e.g., in a private message to the employee or as a websiteavailable to some or all employees of the corporation) at the start ofbusiness on the individual's start date. The HR department may alsoemploy the system in this manner to generate messages for employeepromotions and/or retirements.

In another specific example, a funeral director maintains a list ofclients who have contracted for funeral services at a funeral home aftertheir death. When the system detects the death of one of the clients, asignificant event used as a trigger by the Notification Engine 108, anotification is sent to the funeral director. A draft obituary isprepared by the system using the Analytics Engine 106, including, e.g.,information collected in part by the Communication Engine 110 about theclient from publically available and/or privately accessible sources(e.g., a list of the client's awards, publications, employment history,or other information), materials provided by the client prior to hisdeath (e.g., photographs, essays, or other materials), and/orinformation provided by the funeral director (e.g., contact informationfor the client's next of kin, the name of a preferred charity, or otherinformation). The funeral staff and/or the family of the deceased mayact as editor users to edit the obituary prior to its publication, e.g.,to ensure its accuracy, to ensure that it complies with any family orpersonal sensitivities, to ensure that it includes information theeditor user deems important, or to perform any other sort of review.After finalization, the obituary is published on the website of thefuneral home.

The system can be implemented in a very wide variety of ways. In someexamples, the system is implemented on a social network platform and thepublisher user, editor user, and/or reader users are members of thesocial network. However, the system can also be implemented in a widevariety of other ways as well, some of which do not involve use of asocial network platform, and concepts encompassed in such a system.)

FIG. 3 is a block diagram of an example of a system 300 forcommunicating items, e.g., communicating messages (e.g., multimediamessages) about significant events from a publisher user to a readeruser. In some examples, the publisher user and/or the reader users aremembers of a community that participates in a social network or othertype of community associated with the system. In this example, acomputer network 302 connects a social network provider 304 (such asFacebook® or Google+®) with user devices 306 such as workstations,mobile devices, mobile computers, for communicating across the computernetwork 302. In some examples, the social network provider can be theoperator or host of the system in addition to or instead of an existingsocial network provider. In other examples, the system operatesindependently from any social network and is hosted on a server notshown), and users do not need to be members of a community or socialnetwork to utilize the system.

A publisher user 308 can create, write, dictate, preform, copy, define,or otherwise transcribe media messages, enter instructions aboutcommunication items, criteria, editors, readers, and communicationtimes, for example; give orders to vendors 310 and give orders tostorage modules 312 regarding media communications (we sometimes use theterms communications and media communications interchangeably), andother communication items for delivery to reader users 314 (314A, 314B,. . . , 314M). Publisher-permitted editor users 320 (320A, 320B . . . ,324N) review, modify, augment the media communications and other itemsfor delivery to the reader users 314, as described in more detail below.A Communication engine 110 facilitates identification of the location,status, interest profile (e.g., affinities) and other current andhistorical data of the person described in the communication or for theintended reader users 314 that can be accessed by an authenticatedpublisher user 308. For example, an employer may learn about the hobbiesor recreational activities of a new employee. A Notification Engine 108facilitates identification of the significant events of individuals ofinterest to an authenticated publisher user 308. For example, aNotification Engine 108 scans various data sources (e.g., websites;periodicals such as newspaper websites, magazine websites, andscientific journal websites; and/or social networking facilities) upondemand or on a periodic basis, e.g., daily, to identify information(e.g., news items) associated with specified individuals, e.g.,individuals on a list of individuals to be tracked. Analytics Engine 106uses information from various databases to facilitate the composition,by the publisher user 308, of an appropriate communication item to bedelivered, published, or otherwise provided to reader users 314.

In some examples, the social network provider 304 supplies a databaseserver 316 to the computer network 302. The database server has one ormore databases 318 [318A, 318B, . . . , 318N], for storing a widevariety of information useful for or related to the operation of thesystem, including user instructions, orders, and media messages as wellas the profile and historical data of socially networked individualstogether with information on vendors and distributors and the logisticsinvolved in facilitating the messaging capability provided by thesystem.

FIG. 4 is a block diagram of a network-based digital storage component400 including a storage module 312 for the system 300. The storagemodule 312 provides a secure facility for storage of communicationitems, such as digital multimedia, scanned documents or photographs, anda wide variety of other items, for social publishing and othercommunication from one person to another as facilitated by the system300. For instance, each publisher user is assigned a digital capsule inthe storage module 312 for storage of digital materials such as text,photographs, videos, scanned documents, recorded conversations, andother digital materials. If the publisher user responded to promptsprovided by the system, the user's responses to those prompts are alsostored in the user's digital capsule. A database server 404 in thestorage module 312, connected to the computer network 302, stores a widevariety of information including information associated with inventory,transaction history, status, and scheduled delivery dates forcommunication items stored in the storage module 312. A database server404 stores digital media in a database 406. The information on theserver may be replicated to an offsite server for backup redundancy,

FIG. 5 is an example publisher curating interface 500 of the system 300.The publisher's user device 306 displays the publisher cunning interface500, which provides an editing capability to a publisher. Through thepublisher curating interface 500, a publisher can set up identificationfor notifications by selecting or specifying significant event persons;curate information about a significant event person into a message for areader by inserting or deleting text, images, video into a multimediamessage and rearranging the display of the components of the multimediamessage; selecting a reader from a list of potential readers; and/orcontrol the communication and/or delivery of the message to the reader.For instance, the curating window 502 allows the publisher user toinsert pictures, shapes, text, animation video, sound or any othermultimedia object. The publisher communication interface 500 is alsooperable to transcribe or edit media messages, which may be in the formof e-mail, voice, images, scanned or real-time photographs, or video.The messages may be served up by the Analytics Engine 106 as the resultof searching various data sources for relevant information, as describedin greater detail below. The publisher communication interface 500 mayalso be made available to an editor user 320B for review, revision,approval, and/or commenting on the communication item generated by thepublisher user. Alternatively, a distinct editor communication interfacemay be provided, as described in more detail below.

The Communication engine 110 of the system 300 determines the location,status, and/or affinities and other current of historical information ofthe significant event person and of the reader user.

The Analytics Engine 106 may be employed to assist the publisher user inselecting a delivery date (e.g., by using historical data to forecastpersonal milestones of a reader user, by analyzing news articles orsocial networking facilities to identify the occurrence of a significantevent, or by another method); an appropriate communication item fordelivery (e.g., by identifying information about or associated with thesignificant event person that is appropriate for inclusion in a messageabout the particular significant event or by forecasting future needsand wants of a reader user); delivery times (communication times) bestsuited for the reader user; and/or delivery methods (e.g., the readeruser's most recent email address or phone number).

Example media messages include congratulations on promotions orachievements, autobiographical summaries, obituaries, sympathy notes,birthday wishes, welcome messages to new employees, or other messages.For instance, if the publisher user is an agent of a corporation or aninstitution such as a school, a city, state or federal government, anexample video media message may be emailed to new employees or newclients as a welcome message. In some examples, a media message mayinclude last words or a more extensive message from a publisher user tohis survivors, such as the publisher user's children, including thepublisher user's autobiography to be delivered in full or released instages.

FIG. 6 illustrates an example of an editor's interface 600 of the system100. The user device 306 displays an editor's media message selectionand modification interface 600, which provides an editing window 602allowing the editor user 320A to select a publisher's communication forviewing, revising, approving, or commenting upon. The interface 600maybe a shareable web editor designed for collaboration via Internetaccess to the document Sky Drive® by Microsoft®, or Google Drive® forGoogle® Docs). The editor user may be the same person as the publisheruser or may be another person designated by the publisher user. Theediting selection interface 600 allows the editor to review, modify,correct, amend or add to the message composed by the publisher user.Upon completion of the editor's task, the revised media message is savedand can be served up to the publisher user for delivery to a reader orsent directly to a reader, who may have been preselected by thepublisher user.

FIG. 7 is a block diagram of a Communication engine 110 of the system300. The Communication Engine 110 facilitates identification of asignificant event person and provides criteria used by the NotificationEngine 108 to trigger notification of the curator for composing amessage, publishing or delivery of communication items) for a publisheruser 108 by providing information about a reader user's physicallocation, profile interest information, and/or affinity informationincluding current or historical data on purchase transactions, income,socio-economic status, voter registration or other information that isweb-accessible. In some examples, the location, interest, and affinityand other current and historical information may be displayed by adisplay module 704 on a webpage belonging to or accessible by thepublisher user. The communication engine 110 includes an affinitydatabase 702 for storing significant event person and reader useraffinity information and a reader location database 710 for storing thephysical location of a reader user. The reader location database 710 mayreceive data relevant to the location of a reader user from a GPStranslation module 706 or may obtain the reader user's location from theAnalysis Engine's analysis of websites or other sources of information.For example, the publisher user may have composed a sympathy noteregarding an individual killed in an accident; the Communication enginedetermines that the next of kin is traveling in another country and thuslikely to be reachable by email but not by phone.

FIG. 8 is a block diagram of the Analytics Engine 106 of the system 300.The Analytics Engine 106 facilitates identification and notification ofbigger events for significant event persons, curation of an appropriatemessage upon notification, and publication or delivery of communicationsin response to a significant event on behalf of publisher user 308 byinferring information about the person described in the communicationitem from one or more data sources or determining or inferring milestoneevents fix the reader user 314 or for the person described in thecommunication item, among other things. The person described in thecommunication item may be the intended reader of the communication item,the publisher of the communication item, both the reader and thepublisher, or neither the reader nor the publisher.

A predictive analytics module 802 in Analytics Engine 106 applies searchalgorithms and forecasting models stored in a search and forecastingmodels library 806 to analyze present and/or historical subject userdata in view of data stored in a database 808 containing data related toidentify milestone events and to suggest appropriate media messages oritems for a reader user. The predictive analytics module 802 implementsa variety of forecasting techniques beyond simple algorithms, such asfuture date calculation, including statistical techniques such asmachine learning (e.g., as applied by IBM's Watson computer), gametheory, and data mining, to analyze current and historical data todetermine significant event triggers for notification, to makepredictions about future readers, to identify communication mediamessages, and to identify appropriate delivery times and methods, amonga wide variety of other analyses and algorithms. For example in the caseof an autobiographical communication item of a grandfather (thepublisher user), the reader user is the projected offspring of a currentmember in the system but the publisher user may incapacitated at thetime of publication and delivery or both. By a computer-implementedmethod, data relevant to the publisher user may be extracted from hisprofile in the system 300 and/or generated implicitly based, at least inpart, on the publisher user's stored profile together with historicaldata by a predictive analytics algorithm based on historical data. Basedon the extracted or generated data, a significant event is identified,content for a communication is selected, appropriate reader users areidentified, and/or other analysis is performed, in some cases withoutinput from the publisher user.

In some examples, Analytics Engine 106 may use data specific to a userto identify potential milestone events (e.g., to identify a bar mitzvahdate for a child based on the child's birth date or to identifyappropriate religious holidays based on the user's specified religiousaffiliation or a prevailing religion in the region where the userlives). In some cases, the predictive analytics module 802 may alsoincorporate present or historical data or both to identify relevantinformation for the communication subject or reader user or both thatare in keeping with preferences of the publisher user. In otherexamples, the Analytics Engine 106 analyzes publically available sourcesof information and/or private sources of information to which it hasaccess, including, e.g., social networking facilities, online or mobileperiodicals such as newspapers or magazines, and websites, to identifythe occurrence of significant events associated with the reader user orwith the person whom the communication is about. For instance, theAnalytics Engine 106 may analyze trade journal websites to set upcriteria so the Notification Engine 108 can identify when a targetperson receives an award or a promotion.

A display module 804 of the Analytics Engine 106 may display thesignificant events of an individual of interest (e.g., a reader user oranother individual specified by the publisher user) on a webpagebelonging to or accessible by the publisher user. These events withassociated actions can be selected for notifications stored in theNotification Engine 108. In some embodiments, upon notification by theNotification Engine, the Analytics Engine 106 may automaticallycommunicate messages of a significant event relevant to a reader user,such as a birthday, to the Communication Engine 110, which sends thenotices to relatives of the reader user, who can act as publisher users.The Analytics Engine may use information about a reader user found invarious databases to determine when to send out the notices.

In some embodiments, the predictive analytics implemented by theAnalytics Engine incorporate the robust, optimizing forecastingtechniques of Pinto et al. (U.S. Pat. No. 7,499,897, issued on Mar. 3,2009; U.S. Pat. No. 7,562,058, issued on Jul. 14, 2009; U.S. Pat. No.7,725,300, issued on May 25, 2010; U.S. Pat. No. 7,730,003, issued onJun. 1, 2010; U.S. Pat. No. 7,933,762, issued on Apr. 26, 2011; and U.S.patent application Ser. No. 10/826,949, filed Apr. 16, 2004, thecontents of all of which are incorporated herein by reference), thatmanage historical data using missing values, which must be inferred.

The Analytics Engine can act as a surrogate for the publisher user 308by specifying communications and services or any other communicationitems for placement into storage. Provided the potential reader user 314is registered in the system 300, the Communication Engine 110 willdetermine the location of the reader user, e.g., by GPS tracking orsimilar means. The reader user's interests and status may be availablein the reader user's profile, which, taken together with historicaldata, enable the Analytics Engine 106 utilizing inferences from missingdata, if necessary, to determine an appropriate gift to accompany themessage and an optimal time for delivery. The delivery time is selectedby a predictive analytics algorithm, based on historical data specificto the reader user.

In some embodiments, the Analytics Engine acts as a surrogate of apublisher user 10 to generate communication items (e.g., messages,sympathy tribute selections, and/or delivery instructions) based ondata, e.g., historical data, specific to the reader user. For instance,the Analytics Engine maybe configured as described by Gruber et al.(U.S. patent application Ser. No. 12/987,982, filed Jan. 10, 2011, thecontents of which are incorporated herein by reference) to include anautomated assistant receiving user input; an active ontology withrepresentations of concepts and relations among concepts drawn fromvarious databases of historical data (for instance, for the case inwhich the publisher user is the agent of a corporation, the corporatepersonnel database may be referenced); and a language interpreterparsing the publisher user input to derive a representation of publisheruser intent in terms of the active ontology together with a servicesorchestration to output responses and instructions to implement thepublisher user's intent. In the example of FIG. 6, the reader user isthe projected offspring of a current member of the system and thepublisher user, who wants to send a birthday greeting to the readeruser, is incapacitated, at the reader user's birthday. By acomputer-implemented method, data relevant to the reader user may beextracted from his profile, generated implicitly based, at least inpart, on the reader user's stored profile with the system together withhistorical data by a predictive analytics algorithm based on historicaldata, and/or obtained from publically available or privately accessibleinformation sources. Based on the extracted or generated data acommunication is selected, generated, and delivered, in some caseswithout input from the publisher user.

FIG. 9 is a block diagram of a Notification Engine 108 of the system300. The Notification Engine 108 facilitates publishing or delivery ofcommunications for a publisher user 308 by detecting significant eventsof individuals significant to the publisher as listed in a data file902. For example, a publisher user may be notified about the death offriend by means of a search module 904 supported by a parsing andinterpretation library 908. The publisher user may then compose andpublisher or deliver a sympathy message to the friend's family. In someexamples, information the individual whose significant event has beendetected (referred to here as the tracked individual) may be displayedby a display module 906 on a webpage belonging to the publisher user.The Notification Engine 108 may also display the tracked individual'sprofile within the system 300 for confirmation of the individual'ssignificant event. The Notification Engine 108 includes a trackedindividual affinity database 112B for storing tracked individualaffinity information

As an example, the publisher user is an agent of a corporation; e.g.,the publisher user is a Human Resources professional. The data lists ofthe Notification Engine 108 include current employees, retiredemployees, and newly hired employees who have not yet started to work.The Notification Engine identifies a newly hired employee whose startdate is in the future and alerts the publisher user or another module ofthe system 300. The publisher user composes a welcome notice from atemplate on behalf of the chief executive officer. The welcome noticealso includes automatically integrated material, such as a listing ofthe new employee's awards, education, or employment history, assembledfrom various data sources by the Analytics Engine to personalize themessage. The message is then reviewed by an associate of the publisheruser and scheduled for publication or delivery on the employee's startdate. In some cases, publication or delivery is scheduled with the aidof the Communication Engine, e.g., to account for the new employee'stime zone and location in scheduling the publication or delivery.

FIG. 8 is an example reader display interface 1000 for the example inwhich the reader user is a member of a social network implementing thesystem 300. A reader delivery display 1002 indicates the arrival of acommunication or delivery of a communication item. A reader displaywindow 1002 shows the multimedia message that the publisher 308 hasdelivered. A similar process occurs in the case of a sympathy tribute orother item, particularly when the item is a vendor coupon that isprintable. The reader user 314B is given the opportunity to arrange fordelivery, for example by a common carrier such as FEDEX, UPS, DHL, orthe USPS. Alternatively, the reader user is put into contact with thevendor of the physical or digital item to arrange for delivery. In otherexamples, the reader user is notified directly about the publication ordelivery of a communication item, for instance, via an email message tothe reader user's email address or a phone call or SMS to the readeruser's mobile phone.

FIG. 11 is a flowchart of an example process 1100 for communicating amultimedia message in the system 300. In the process 1100, a publisheruser 308 identifies a Significant Event Person (Step 1102) then requeststhat person's profile from the Communication Engine 110 (Step 1104).With that profile and other additional information, the publisher user308 configures a notification event that is saved in the NotificationEngine's database (Step 1106). There is a pause in the action until theNotification Event occurs. (Step 1108). Upon notification (Step 1110),the publisher starts assembling a communication by identifying thereader (Step 1112) by requesting a profile (Step 1114). Then thepublisher curates the communication from the selected information andadditional input (Step 1116). The communication draft is edited (Step1118) and served back to the publisher who selects a delivery time (Step1120) and then queues up the communication for publication (Step 1122).

For instance, an attorney monitoring a list of his clients receivesnotification that one of his clients has received a promotion. Thepublisher user composes a message to be sent to the individual, e.g., byfilling in a template with publisher-generated content (e.g., apersonalized message) together with information about the individualfrom various data sources supplied by direct search by the CommunicationEngine and/or with the help of the Analytics Engine 106. For instance,the attorney may compose a congratulatory message to his clientfollowing a template, include press releases about the client'spromotion collected by the Analytics Engine, and add a paragraphinquiring about additional business opportunities facilitated by theclient's new position. An editor reviews and revises the message (Step903). For instance, the attorney's associate as a designated editor 320Breviews the saved message and makes a minor emendation. The publisheruser conducts a final review of the message and sends the message orarranges for the system to send the message on his behalf in some caseswith the help of the Communication Engine. The Communication Engine 110directs the message to the reader user at his current location (e.g.,the message is directed to the attorney's client, who is presentlystaying at a hotel in Shanghai. The reader user 314D receive and readsthe message. The reader user may be given the opportunity to acknowledgereceipt and confirm delivery and even reply to the publisher user 308 orto his proxy.

FIG. 12 is a flowchart of an example process 1200 for commenting upon acommunication item. In this example, the system is used to compose anobituary for a deceased individual to be published on a websiteaccessible to relatives, colleagues, and friends of the deceased user.The next of kin as publisher user 308 composes an obituary and publishesthe obituary on a website hosted by the system 300. The publisher user108 sets up the restriction that relatives, colleagues and friendsdesignated as editors can append comments to the obituary but cannotalter the main con tent of the obituary. The publisher user 108 receivesnotification of the individual's death either directly or through theNotification Engine 108 (Step 1210). The publisher user then composesthe obituary drawing on various data sources at times with the aid ofthe Communication Engine 110 and the Analytics Engine 106 (Step 1212)and saves the obituary. In some examples, the obituary is directlypublished to reader users 314 (Step 1220) on a website hosted by thesystem 300. In other examples, the obituary is published for editorialcomments by editor users 320 (Step 1216) subject to review by thepublisher user 308 (Step 1220) before general publication to readers 314(Step 1220). In some cases, after publication to reader users, commentscan be added by editor users without further review (Step 1218).

FIG. 13 is a flowchart of an example process 1300 for distributing atribute or gift in the system 300, in the process 1300, a publisher user308 receives notification of a significant event occurring to anindividual of interest either directly or with the help of theNotification Engine 108 (Step 1310). The publisher user 308 composes acommunication item for a selected reader 314D drawing on various datasources at times with the help of the Communication Engine 110 and,Analytics Engine 106 (Step 1316). For example, the significant event isthe death of an individual on the data list of significant individualsfor the publisher user 308 and the intended reader user 314D is the nextof kin of the deceased individual. To accompany the publication ordelivery of the communication item, e.g., a sympathy note, the publisheruser 308 selects a tribute or gift for the selected reader 3140, drawingupon the preference and affinities of the reader either directly or withthe help of the Communication Engine 110 (Step 1318). For example, afloral arrangement may be ordered or a donation may be made to acharitable organization designated by the deceased individual or by theselected reader 314D. The publisher user 308 delivers the communicationitem (Step 1324) and arranges with a vendor 310, which in this examplemay be a florist or floral delivery service or charitable organization(Step 1322). The reader user 314D may be given the opportunity toacknowledge receipt and confirm delivery and to reply to the publisheruser 308 or the publisher user's proxy (Step 1326).

In some embodiments, the publisher user 308 is an agent of a corporationor other entity who sends a communication item to current or pastemployees in good standing, e.g., congratulatory message including stockoptions, or, more personally, an award or achievement plaque. In someembodiments, the Analytics Engine acts as a surrogate of a publisheruser 308 in that the Analytics Engine is configured to generate acommunication. For instance, for a publisher user who is an agent of acorporation, the Analytics Engine uses the corporate personnel databaseto identify reader users and, based on their profiles, select anappropriate communication, e.g., congratulations or achievement or othervaluable communication.

In some instances, the system operates within a social network of familymembers. The publisher user may be a member of an older generation andthe reader user may be a member of a younger generation. In some cases,the intended reader user is not yet a member of the social network,either because the reader user has not yet enrolled or because thereader user has not yet been born in some cases, the publisher user maybe incapacitated or even dead at the time of delivery (e.g., thepublisher user may be an incapacitated or dead grandparent of the readeruser). If the publisher user is incapacitated or dead, the system maycarry out the instructions of the publisher user and requestconfirmation as appropriate from a designated proxy of the publisheruser, such as a parent of the reader user or an executor of thepublisher user's estate. In some cases, the system requests confirmationof the identity and/or role of the designated proxy. For instance, ifthe executor of the publisher user's estate logs into the system usingthe deceased publisher user's credentials, the executor may beconsidered to have been authenticated as the publisher user's proxy.

In some instances, the publisher user is an institution or other entityor an agent of such an institution or other entity, such as a school ora city, state, or federal government; or a company, or a trust orfoundation, or a non-profit organization, for example. The reader usermay be a current employee in good standing or a past employee, e.g., aretiree or someone who was terminated or resigned, or a current or pastindividual client. For a variety of reasons the institution or entitymay find it useful to maintain a relationship with the employee and tocommunicate items at communication times to the employee or client tomaintain the relationship. For instance, the publisher user may use thesystem to send a message to the reader user, such as a holiday greeting,a message of congratulations on a promotion, a greeting for a birthdayor other anniversary, a reminder of a spouse's or child's birthday, or asuggested message to be forwarded to the spouse or child. The publisheruser may also use the system to communicate a sympathy message to thereader user's next of kin upon the death of the reader user.

In some cases, the Analytics Engine may ad as a surrogate for thepublisher user and may use the corporate personnel database to identifyreader users and, based on the profiles of the reader users, determineappropriate milestones and/or communications. For instance, an AnalyticsEngine customized to a particular company may track the addresses, emailaddresses, or other contact information of past employees or clients toenable the company, to maintain relationships with the past employees.In other examples, the system may provide an employee feedback portalfor a company, in which employees of the company (acting as publisherusers) submit suggestions, complaints, or comments, which are thenforwarded, singly or in aggregate, to the human resources department(acting as the reader user) of the company.

In other instances, the system is used by a group of people, such as agroup of friends, acquaintances, coworkers, or another group of people.For instance, a friend may act as a publisher and arrange for thedelivery of a birthday greeting to another friend through the system.

In some instances, when the system is a social network implementedsystem, the system enables the communication of items from a publisheruser to a reader, who may not necessarily be a member of the socialnetwork or user of the system, through a proxy reader user who is amember or user of the social network or system. For example, agrandfather may use the system to set up the delivery of a birthdaygreeting to his two-year-old granddaughter on her tenth birthday. Thegrandfather dies before the granddaughter turns ten. When thegranddaughter does reach her tenth birthday, she is too young to enrollin the system. The analytics module is able to determine thecommunication item and the delivery (communication) date (thegranddaughter's tenth birthday), but is unable to send a deliverymessage to the granddaughter directly because she is not a member of thesystem. The analytics module can identify the granddaughter's parents asproxies for the granddaughter and send the delivery message to theparents. For instance, the parents may be automatically considered theproxy of the reader or may be asked to provide authentication of theirrelationship with the reader prior to being considered the proxy of thereader. In some cases, the parents, as proxy for the reader, may beasked to approve the relationship between the reader and the publisheruser and/or the appropriateness of the communication item.

In some instances of the use of the system, the publisher may be thesame person as the editor. For example, the publisher composes his ownsummary of his significant events as a future memorial or obituary.

Implementations of the system are not limited to social networks or neednot span multiple generations, but some implementations will be in thecontext of social networks or will be multigenerational or both.

As desired, the system may include more or fewer than the componentsillustrated.

The system is described above with reference to block and flow diagramsof systems, methods, apparatuses, and/or computer program productsaccording to examples. In some instances, the publisher and reader usersmay access the system by desktop or laptop computers. In someembodiments, the publisher and reader users may access the system bymobile devices such as smart phones. In some embodiments, the publisherand reader users may access the system by tablet computers or anycommercial computing device connected to the internet. In some cases,the system may be constructed to operate on the internet independent ofexisting systems. The significant event system may operate usingexisting social networks, e.g., Facebook®, Google+®, or Yammer™ asplatforms using existing application interfaces open to websitedevelopers.

One or more blocks of the block diagrams and flow diagrams, andcombinations of blocks in the block diagrams and flow diagrams,respectively, can be implemented by computer-executable programinstructions. Some blocks of the block diagrams and flow diagrams maynot necessarily need to be performed in the order presented, or may notnecessarily need to be performed at all, in sonic cases.

These computer-executable program instructions may be loaded onto ageneral-purpose computer, a special-purpose computer, a processor, orother programmable data processing apparatus to produce a particularmachine, such that the instructions that execute on the computer,processor, or other programmable data processing apparatus create meansfor implementing one or more functions specified in the flow diagramblock or blocks. These computer program instructions may also be storedin a computer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instruction meansthat implement one or more functions specified in the flow diagram blockor blocks. As an example, embodiments may provide for a computer programproduct, comprising a computer-usable medium having a computer-readableprogram code or program instructions embodied therein, saidcomputer-readable program code adapted to be executed to implement oneor more functions specified in the flow diagram block or blocks. Thecomputer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational elements or steps to be performed on the computer or otherprogrammable apparatus to produce a computer-implemented process suchthat the instructions that execute on the computer or other programmableapparatus provide elements or steps for implementing the functionsspecified in the flow diagram block or blocks.

Accordingly, blocks of the block diagrams and flow diagrams supportcombinations of means for performing the specified functions,combinations of elements or steps for performing the specified functionsand program instruction means for performing the specified functions. Itwill also be understood that each block of the block diagrams and flowdiagrams, and combinations of blocks in the block diagrams and flowdiagrams, can be implemented by special-purpose, hardware-based computersystems that perform the specified functions, elements or steps, orcombinations of special purpose hardware and computer instructions.

While the system has been described in connection with certain examples,is the system is not limited to the disclosed embodiments, but on thecontrary, includes various modifications and equivalent arrangements.Embodiments of the subject matter and the functional operationsdescribed in this specification can be implemented in digital electroniccircuitry, in tangibly-embodied computer software or firmware, incomputer hardware, including the structures disclosed in thisspecification and their structural equivalents, or in combinations ofone or more of them. Embodiments of the subject matter described in thisspecification can be implemented as one or more computer programs, i.e.,one or more modules of computer program instructions encoded on atangible non-transitory program carrier for execution by, or to controlthe operation of data processing apparatus. Alternatively or inaddition, the program instructions can be encoded on an artificiallygenerated propagated signal, e.g., a machine-generated electrical,optical, or electromagnetic signal, that is generated to encodeinformation for transmission to suitable receiver apparatus forexecution by a data processing apparatus. The computer storage mediumcan be a machine-readable storage device, a machine-readable storagesubstrate, a random or serial access memory device, or a combination ofone or more of them.

The term “data processing apparatus” encompasses all kinds of apparatus,devices, and machines for processing data, including: by way of examplea programmable processor, a computer, or multiple processors orcomputers. The apparatus can include special purpose logic circuitry,e.g., an FPGA (field programmable gate array) or an ASIC (applicationspecific integrated circuit). The apparatus can also include, inaddition to hardware, code that creates an execution environment for thecomputer program in question, e.g., code that constitutes processorfirmware, a protocol stack, a database management system, an operatingsystem, or a combination of one or more of them.

A computer program (which may also be referred to or described as aprogram, software, a software application, a module, a software module,a script, or code) can be written in any form of programming language,including compiled or interpreted languages, or declarative orprocedural languages, and it can be deployed in any form, including as astandalone program or as a module, component, subroutine, or other unitsuitable for use in a computing environment. A computer program may, butneed not, correspond to a file in a file system. A program can be storedin a portion of a file that holds other programs or data, e.g., one ormore scripts stored in a markup language document, in a single filededicated to the program in question, or in multiple coordinated files,e.g., files that store one or more modules, sub programs, or portions ofcode A computer program can be deployed to be executed on one computeror on multiple computers that are located at one site or distributedacross multiple sites and interconnected by a communication network.

The processes and logic flows described in this specification can beperformed by one or more programmable computers executing one or morecomputer programs to perform functions by operating on input data andgenerating output. The processes and logic flows can also be performedby, and apparatus can also be implemented as, special purpose logiccircuitry, e.g., an FPGA (field programmable gate array) or an ASIC(application specific integrated circuit).

Computers suitable for the execution of a computer program include, byway of example, can be based on general or special purposemicroprocessors or both, or any other kind of central processing unit.Generally, a central processing unit will receive instructions and datafrom a read only memory or a random access memory or both. The essentialelements of a computer are a central processing unit for performing orexecuting instructions and one or more memory devices for storinginstructions and data. Generally, a computer will also include, or beoperatively coupled to receive data from or communication data to, orboth, one or more mass storage devices for storing data, e.g., magnetic,magneto optical disks, or optical disks. However, a computer need nothave such devices. Moreover, a computer can be embedded in anotherdevice, e.g., a mobile telephone, a personal digital assistant (PDA), amobile audio or video player, a game console, a Global PositioningSystem (GPS) receiver, or a portable storage device, e.g., a universalserial bus (USB) flash drive, to name just a few.

Computer readable media suitable for storing computer programinstructions and data include all forms of non volatile memory, mediaand memory devices, including by way of example semiconductor memorydevices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks,e.g., internal hard disks or removable disks; magneto optical disks; andCD ROM and DVD-ROM disks. The processor and the memory can besupplemented by, or incorporated in, special purpose logic circuitry.

To provide for interaction with a user, embodiments of the subjectmatter described in this specification can be implemented on a computerhaving a display device, e.g., a CRT (cathode ray tube) or LCD (liquidcrystal display) monitor, for displaying information to the user and akeyboard and a pointing device, e.g., a mouse or a trackball, by whichthe user can provide input to the computer. Other kinds of devices canbe used to provide for interaction with a user as well; for example,feedback provided to the user can be any form of sensory feedback, e.g.,visual feedback, auditory feedback, or tactile feedback; and input fromthe user can be received in any form, including acoustic, speech, ortactile input. In addition, a computer can interact with a user bysending documents to and receiving documents from a device that is usedby the user; for example, by sending web pages to a web browser on auser's client device in response to requests received from the webbrowser.

Embodiments of the subject matter described in this specification can beimplemented in a computing system that includes a back end component,e.g., as a data server, or that includes a middleware component, e.g.,an application server, or that includes a front end component, e.g., aclient computer having a graphical user interface or a Web browserthrough which a user can interact with an implementation of the subjectmatter described in this specification, or any combination of one ormore such back end, middleware, or front end components. The componentsof the system can be interconnected by any form or medium of digitaldata communication, e.g., a communication network. Examples ofcommunication networks include a local area network. (“LAN”) and a widearea network (“WAN”), e.g., the Internet.

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other.

While this specification contains many specific implementation details,these should not be construed as limitations on the scope of anyinvention or of what may be claimed, but rather as descriptions offeatures that may be specific to particular embodiments of particularinventions. Certain features that are described in this specification inthe context of separate embodiments can also be implemented incombination in a single embodiment. Conversely, various features thatare described in the context of a single embodiment can also beimplemented in multiple embodiments separately or in any suitablesubcombination. Moreover, although features may be described above asacting in certain combinations and even initially claimed as such, oneor more features from a claimed combination can in some cases be excisedfrom the combination, and the claimed combination may be directed to asubcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various system modulesand components in the embodiments described above should not beunderstood as requiring such separation in embodiments, and it should beunderstood that the described program components and systems cangenerally be integrated together in a single software product orpackaged into multiple software products.

Particular embodiments of the subject matter have been described. Otherembodiments are within the scope of the following claims. For example,the actions recited in the claims can be performed in a different orderand still achieve desirable results. As one example, the processesdepicted in the accompanying figures do not necessarily require theparticular order shown, or sequential order, to achieve desirableresults. In certain implementations, multitasking and parallelprocessing may be advantageous.

Other implementations are also within the scope of the following claims.

What is claimed is:
 1. A computer-implemented method comprising notifying a first person that a significant event is going to occur with respect to a second person; receiving from the first person, the second person, or another person a communication that relates to the significant event and to the first person and that has been curated at least in part from information that has been accumulated automatically from online resources, and sending the curated communication to the communication target.
 2. The method of claim 1, further comprising detecting an occurrence of the significant event.
 3. The method of claim 2, further comprising receiving information provided by the first person defining at least one condition for occurrence of the significant event.
 4. The method of claim 2, wherein detecting an occurrence of the significant event includes conducting an automated analysis of publicly available (a) online or mobile social networking facilities, (b) online or mobile periodicals, and (c) websites.
 4. The method of claim 1, wherein receiving the communication includes receiving an approval of an automatically generated communication.
 5. The method of claim 1, wherein receiving the communication includes receiving a communication that has been generated by the first person and that includes at least some of the information that has been accumulated.
 6. The method of claim 1, further comprising receiving an identification of the second person from the first person.
 7. A computer-implemented method comprising in connection with an occurrence of a significant event of a person the conditions for occurrence of which had been defined earlier by a user, automatically generating a page of a website or a mobile application or an email application that is associated with the significant event of the person and includes information generated by and received from the user, information about the person, and information associated with the person that has been obtained by automated analysis of publicly available (a) online or mobile social networking facilities, (b) online or mobile periodicals, and (c) websites, and serving the page for display through a web browser or a mobile application or an email application.
 8. The method of claim 7, wherein the page is served after the user is given an opportunity to curate the page.
 9. The method of claim 8, wherein curating the page includes adding content to the page, removing content from the page, and/or changing content on the page.
 10. The method of claim 7, wherein the page is served to an editor and then re-served after the editor has curated it, and the editor is designated by the user.
 11. The method of claim 7, wherein the page is served without input from the user.
 12. The method of claim 7, wherein notification of the occurrence of the significant event is given automatically to someone, in particular someone who needs to take some action regarding the event.
 13. The method of claim 12, wherein notification of the occurrence of the significant event is given automatically to the user.
 14. The method of claim 7, further comprising detecting the occurrence of the significant event.
 15. The method of claim 7, wherein detecting the occurrence of the significant event includes conducting an automated analysis of publicly available (a) online or mobile social networking facilities, (b) online or mobile periodicals, and (c) websites.
 16. The method of claim 15, wherein conducting an automated analysis includes conducting the analysis in view of information provided by the user defining the conditions for occurrence of the event.
 17. The method of claim 7, wherein the page is served in the future to parties whose existence and identity with respect to the user and the significant event is undetermined at the time when the conditions for occurrence are defined.
 18. The method of claim 7, wherein the user is a service provider and the person is a client of the service provider.
 19. The method of claim 7, wherein the user is an agent of a company, the person is an employee of the company, and the page is served as a corporate email message or as a website on an internal corporate network.
 20. The method of claim 7, wherein the user is an agent of a charitable foundation or university and the person is a donor to the charitable foundation or university.
 21. The method of claim 7, wherein the page includes information that is generated by and received from another user and is about the person.
 22. The method of claim 7, wherein the page includes information that is generated by and received from the person and is about the person.
 23. The method of claim 7, wherein the event is a death of the person.
 24. The method of claim 23, wherein serving the page includes serving the page to a relative of the person.
 25. The method of claim 7, wherein the event is a birthday or anniversary of the person.
 26. The method of claim 7, wherein the event is a change in employment status of the person.
 27. The method of claim 7, wherein serving the page includes delivering a notification of the page to a recipient via a private communication.
 28. The method of claim 27, wherein the recipient is the person.
 29. The method of claim 27, wherein the private communication channel includes email, telephone, short message service (SMS) messaging, and/or social network facilitated communication.
 30. The method of claim 7, wherein serving the page includes publishing the page as a website.
 31. The method of claim 7, wherein the website is available to a group of people sharing a common affiliation. 